addRoutes: optional parameter overwriteNames
#1129
Conversation
|
@fnlctrl @yyx990803 If other parameters may arise in the future, we should use an object instead of a boolean |
|
I'm a bit confused by your use case. By "dynamic url translations" do you mean the user picks a different language after the app starts? Can you provide more details e.g. what the usage code looks like? |
|
@yyx990803 yes exactly. Here is an example jsfiddle: https://jsfiddle.net/3r9oh2mz/48/ In this example if the |
|
I forgot |
|
Hello dear friends! Have I totally missed something or is this not pulled yet? And if so, why not yet? |
|
@posva @fnlctrl @yyx990803 If this way of dynamically translating urls is considered too hacky/dirty no worries just let me know and I will close this PR and open an issue for a "dynamic url translations" feature request instead. But only if that's not a way to bury this feature 😉 |
|
Well I am not sure If i am qualifed to say if it is hacky. But might git clone this and try tomorrow. :) |
|
2.4.0 added a new parameter in |
Simply added an optional boolean parameter
overwriteNamesto theaddRoutefunction.When this parameter is set to true, adding a route with a duplicate name will be allowed and replace the name entry in
nameMap.This tiny change has great effects because it allows dynamic url translations (as long as the links use route names instead of pathes).
For instance:
mysite.com/en/records(routes names with English urls)mysite.com/fr/enregistrements(after routes names overwritten with French urls)Overwriting route names was the default behaviour of vue-router 1.X
router.on(), and this was the only way I have ever found to achieve dynamic url translations.Lots of people in non-english speaking countries need url translation, because english names are sometimes not obvious for them, and because of SEO reasons too.
I also fixed a typo in the existing docs of addRoutes.
Let me know if you want me to document this new parameter, I'd be glad to make a PR.
Laurent.